I am trying to move mailboxes from one 2010 box to another but it is failing with the above error. I executed the command: Get-MailboxDatabase | Add-ADPermission -User "Administrator" -AccessRights ExtendedRight -ExtendedRights Receive-As, ms-Exch-Store-Admin Thinking that this is a permission issue but it still fails. What did I miss? Bert

Hi Peeny, Can you try this go into ad users and computers tools - view advanced then view the properties of the user account that failed go to the security tab and advanced button make sure the "allow inheritible permissions" is checked Thanks, SanthoshSanthosh Sivaraman MCITP: Microsoft Exchange Server 2007/2010 | MCSE/MCSA

is this RTM or SP1? Here is a post in our DigiScope documentation that may help point you in the right direction with explicit PS commands etc http://www.lucid8.com/download/documentation/DSWebHelp/DigiScopeHelp.htm#SETUP/Granting_Access_to_Exchange_2010_Production_Databases_Mailboxes.htm Troy Werelius www.Lucid8.com

Santhosh - No, it wasn't selected but it is now. Unfortunately it made no difference. It still fails with the same error. Troy - I ran those commands and it seemed to work fine but as I mentioned above, the move still fails. Bert

Are you running 2010 RTM or SP1 on each of the 2010 servers? I would highly recommend that you run SP1 since many changes/fixes were made What exact command are you using to start the move? Troy Werelius www.Lucid8.com

Troy - The box I am trying to move from is SP1. The box I am trying to move to is RTM. I am not using the powershell, I am using the GUI. Having said that, some mailboxes are moving now. It is slow going but I can move a few at a time. I checked the permissions and they seem to be updated witht he admin having full access permission. Bert

I would strongly suggest that you upgrade the RTM box to SP1 I have seen several threads on various and multiple issues trying to move mailboxes between RTM and SP1 boxes. I am sure its possible to do, however, why bloody yourself over it, upgrade and then rerun the moves BTW as a side note and shameless plug when you get some time check out Lucid8's DigiScope http://www.lucid8.com/product/digiscope.asp that has the ability to open a raw Exchange Database from as little as an XP or Windows 7 Desktop so that you can Browse, Search, Export to PST, MSG & XML or Recover mailboxes and granular data directly to ANY production Exchange server (even different versions. If you are pressed for time check out this 7 minute flash demo http://l8downloads.com/FLASH/DSWEB/DigiScope_Overview.html Troy Werelius www.Lucid8.com

Thanks, Troy. I am int he process of applying SP1 to the new box now and I will continue with the moves once that is complete. I will definately have a look at DigiScope. I do have to say that it is a very sad state of affairs when a person has to turn to a third party in order to get a decent GUI for a Microsoft product. I have the sinking feeling that Microsoft is very rapidly becoming a has-been. Bert

Great, I think SP1 application will definitely help and case it will remove the RTM vs SP1 argument I hear you on the GUI standpoint. I think the Powershell commands are great but the real killer way to won the market is to have both a reasonable GUI and then PS for really advanced items That said MS has done an incredible job in many other areas of Exchange and from selfish standpoint I am glad they don't have a nice GUI for export/import :-) since that continues to offer us a great opportunity to build valuable products for our customers. Troy Werelius www.Lucid8.com

<Sigh> The application of SP1 failed: Mailbox Role Failed Error: The following error was generated when "$error.Clear(); if ($RoleIsDatacenter -ne $true) { if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue) { # upgrade the discovery mailboxes to R5 version, this will fix the RecipientDisplayType property of the discovery mailbox which was wrong in R4. get-mailbox -RecipientTypeDetails DiscoveryMailbox -DomainController $RoleDomainController | where {$_.IsValid -eq $false} | set-mailbox -DomainController $RoleDomainController $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName; $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName; $mbxs = @( get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 ); if ( $mbxs.length -eq 0) { $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController); if($dbs.Length -ne 0) { $mbxUser = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1); if ($mbxUser.Length -ne 0) { enable-mailbox -Discovery -identity $mbxUser[0] -DisplayName $dispname -database $dbs[0].Identity; } } } } else { write-exchangesetuplog -info "Skipping creating Discovery Search Mailbox because of insufficient permission." } } " was run: "Database is mandatory on UserMailbox. Property Name: Database". Database is mandatory on UserMailbox. Property Name: Database Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=ms.exch.err.Ex88D115&l=0&cl=cp Error: The following error was generated when "$error.Clear(); if ($RoleIsDatacenter -ne $true) { if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue) { # upgrade the discovery mailboxes to R5 version, this will fix the RecipientDisplayType property of the discovery mailbox which was wrong in R4. get-mailbox -RecipientTypeDetails DiscoveryMailbox -DomainController $RoleDomainController | where {$_.IsValid -eq $false} | set-mailbox -DomainController $RoleDomainController $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName; $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName; $mbxs = @( get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 ); if ( $mbxs.length -eq 0) { $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController); if($dbs.Length -ne 0) { $mbxUser = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1); if ($mbxUser.Length -ne 0) { enable-mailbox -Discovery -identity $mbxUser[0] -DisplayName $dispname -database $dbs[0].Identity; } } } } else { write-exchangesetuplog -info "Skipping creating Discovery Search Mailbox because of insufficient permission." } } " was run: "Database is mandatory on UserMailbox. Property Name: Database". Database is mandatory on UserMailbox. Property Name: Database Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=ms.exch.err.Ex88D115&l=0&cl=cp Elapsed Time: 00:02:43 Bert

Great, I think SP1 application will definitely help and case it will remove the RTM vs SP1 argument I hear you on the GUI standpoint. I think the Powershell commands are great but the real killer way to won the market is to have both a reasonable GUI and then PS for really advanced items That said MS has done an incredible job in many other areas of Exchange and from selfish standpoint I am glad they don't have a nice GUI for export/import :-) since that continues to offer us a great opportunity to build valuable products for our customers. Troy Werelius www.Lucid8.com 1. As I mentioned above, the application of SP1 has failed. I have a user (DiscoverySearchMailbox) whose HomeDB attribute is not set. 2. I just don't understand how one company can produce a product with an absolutely EXCELLENT GUI management tool (SQL Server) and one that sucks big time (Exchange 2010). Especially when earlier versions of the same product had very usable GUI's 3. I agree 100%. PowerShell is an excellent idea. BUT, I did my apprentiship in the Unix trenches many years ago and I have no desire to go back. One of the reasons I moved to Microsoft all those years ago is precisely because I didn't have to do all that command line garbage unless I wanted to. I tried earlier to set the full access permission on multiplr users and you can't do that in the console.. This is not a new idea. Microsoft consoles have had that capability for almost 15 years and Exchange 2010 can't do it?????? 4. I also agree on the technical quality of Exchange 2010. But that does me absolutely no good at all if I can't administer it effectively. Netware was a technically excellent product and it is all but gone because they didn't address the needs of the rank and file admins. ____, look at the garbage in the setup log when the SP1 install failed: PS code!!! WTF??? I don't want PS code. I want to know what went wrong and what I need to do to fix it. Unfortunately, the hyperlink provided in the GUI just tells me that it knows nothing of the error. Thanks alot.... Bert

Did some research and found that others have this same issue it is directly related to the DiscoverySearchMailbox that is installed during the Initial Installation of Exchange. Most show that it does not have a homeMDB attribute assigned to it. (No Database) Check out these threads I think they will help greatly http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/10ad4a1e-3108-4016-85cc-8e679e2e8fc9 http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/0728ad9c-16be-423e-9bbe-fb0c6fc0d5ca Totally agree on 2-4 and yes they are making a hug drive away from the GUI back to command line which I agree is bizarre since thats the old way of doing things. Sure it can be very powerful if you really need advanced actions but sheesh forcing you to use PS is not a good position IMO. NOTE: I saw that special link to no solution they posted. That was really pathetic IMO and I will ping the Exchange team to advise Troy Werelius www.Lucid8.com

Thanks for the assistance, Troy. I was able to finally get SP1 applied and I moved all of the mailboxes. I could only move a few at a time, though, because I kept getting the "No Access" error. After I moved all of the mailboxes, the dreaded federatedemail box remained and I couldn't do a thing with it - every time I tried to move it, I go tthe same no access error. So, I deleted it and decommissioned the box. I then ran setup /preparead to reestablish the federatedemail user and all is good. Everything is on the new box. I don't know who is pushing this powershell stuff at Microsoft so hard but I think that s/he should be shot with a ball of his/her own excrement before s/he does some permanent damage to Microsoft. I was reading an article just the other day that pointed out that it used to be that when Microsoft anounced a new release of a product, everyone dropped what they were doing to check it out. Now, it seems that no one cares. Personally, I think a lot of that ambivalence is caused by things such as the deprecation of a GUI console in favor of a comand line which flys in the face of everything Microsoft has stood for over the years. If I wanted to use a command line for all of my administration, I would have moved to a Linux environment years ago. But I don't think anyone at Microsoft is listening, so I guess I'll just shut up and try to find a decent email system somewhere that does what Exchange used to do. Bert

Great news, glad its resolved OMG I totally spit out my water when I read your comment about punishment for the MS PS person LOL. Agreed that it makes very little sense IMO to force PS on everyone. I see the value in it of course but sure would be nice to have the GUI for basic items and then PS for the super advanced. Have a great weekend and it would be great if you would mark any of my comments that helped you as being the answer Troy Werelius www.Lucid8.com

Thanks; I have my moments :-) The only thing PS is missing is an "M" and it would be complete :-) Bert